Sourced from github/codeql-action/init's releases.

v3.37.4

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

v3.37.3

No user facing changes.

v3.37.2

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

v3.37.1

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

v3.37.0

• Update default CodeQL bundle version to 2.26.0. #3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

v3.36.3

No user facing changes.

• a2983b8 Merge pull request #4058 from github/backport-v3.37.4-f205ea1c3
• 30d6d12 Rebuild
• 14e2e60 Update version and changelog for v3.37.4
• 5d3f01e Merge remote-tracking branch 'origin/releases/v4' into backport-v3.37.4-f205e...
• 3f405c7 Revert "Rebuild"
• 19d11a3 Revert "Update version and changelog for v3.37.3"
• f205ea1 Merge pull request #4053 from github/update-v4.37.4-9130ce0f7
• e40d079 Update changelog for v4.37.4
• 9130ce0 Merge pull request #4051 from github/update-bundle/codeql-bundle-v2.26.2
• c62d824 Add changelog note
• Additional commits viewable in compare view

Sourced from github/codeql-action/analyze's releases.

v3.37.4

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

v3.37.3

No user facing changes.

v3.37.2

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

v3.37.1

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

v3.37.0

• Update default CodeQL bundle version to 2.26.0. #3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

v3.36.3

No user facing changes.

• a2983b8 Merge pull request #4058 from github/backport-v3.37.4-f205ea1c3
• 30d6d12 Rebuild
• 14e2e60 Update version and changelog for v3.37.4
• 5d3f01e Merge remote-tracking branch 'origin/releases/v4' into backport-v3.37.4-f205e...
• 3f405c7 Revert "Rebuild"
• 19d11a3 Revert "Update version and changelog for v3.37.3"
• f205ea1 Merge pull request #4053 from github/update-v4.37.4-9130ce0f7
• e40d079 Update changelog for v4.37.4
• 9130ce0 Merge pull request #4051 from github/update-bundle/codeql-bundle-v2.26.2
• c62d824 Add changelog note
• Additional commits viewable in compare view

Sourced from sigstore/cosign-installer's releases.

v3.10.1

What's Changed?

Note: cosign-installer v3.x cannot be used to install Cosign v3.x. You must upgrade to cosign-installer v4 in order to use Cosign v3.

Note: This is planned to be the final release of Cosign v2, though we will cut new releases for any critical security or bug fixes. We recommend transitioning to Cosign v3.

• Bump default Cosign to v2.6.1 (#203)

v3.10.0

What's Changed

• Bump default Cosign to v2.6.0 in sigstore/cosign-installer#200

Full Changelog: sigstore/cosign-installer@v3.9.2...v3.10.0

v3.9.2

What's Changed

• not fail fast and setup permissions in sigstore/cosign-installer#195
• drop old unsupported versions <v2.0.0 in sigstore/cosign-installer#192
• Update default to v2.5.3 in sigstore/cosign-installer#196

Full Changelog: sigstore/cosign-installer@v3.9.1...v3.9.2

v3.9.1

What's Changed

• default action install to use release v2.5.1 by @​cpanato in sigstore/cosign-installer#193
• default cosign to v2.5.2 by @​cpanato in sigstore/cosign-installer#194

Full Changelog: sigstore/cosign-installer@v3.9.0...v3.9.1

v3.9.0

What's Changed

• Bump actions/setup-go from 5.4.0 to 5.5.0 by @​dependabot in sigstore/cosign-installer#189
• bump cosign install to use release v2.5.0 as default by @​cpanato in sigstore/cosign-installer#191

Full Changelog: sigstore/cosign-installer@v3...v3.9.0

v3.8.2

What's Changed

• install cosign v2 from main in sigstore/cosign-installer#186

Full Changelog: sigstore/cosign-installer@v3...v3.8.2

v3.8.1

What's Changed

• use cosign 2.4.3 and other updates by @​cpanato in sigstore/cosign-installer#182

... (truncated)

• 7e8b541 bump to use cosign 2.6.1 (#203)
• d7543c9 Bump default Cosign to v2.6.0 (#200)
• 920f20f Bump actions/setup-go from 5.5.0 to 6.0.0 (#199)
• bb9dfc1 Bump actions/github-script from 7.0.1 to 8.0.0 (#198)
• 074636b Bump actions/checkout from 4.2.2 to 5.0.0 (#197)
• d58896d Update default to v2.5.3 (#196)
• e40248c drop old unsupported versions <v2.0.0 (#192)
• d9374b9 not fail fast and setup permissions (#195)
• 398d4b0 default cosign to v2.5.2 (#194)
• 84f54a2 default action install to use release v2.5.1 (#193)
• Additional commits viewable in compare view

Sourced from ossf/scorecard-action's releases.

v2.4.4

What's Changed

This update bumps the Scorecard version to the v5.5.0 release. For a complete list of changes, please refer to the Scorecard v5.4.0 release notes and the Scorecard v5.5.0 release notes.

• log POST failures instead of failing entire action by @​spencerschrock in ossf/scorecard-action#1625

Full Changelog: ossf/scorecard-action@v2.4.3...v2.4.4

• 2d11466 Bump action tag for v2.4.4 release (#1688)
• 1bd3285 🌱 Bump the docker-images group across 1 directory with 2 updates (#1...
• 913edce 🌱 Bump github.com/containerd/containerd from 1.7.32 to 1.7.33 (#1671)
• 0957b8f 🌱 Bump golang.org/x/net from 0.56.0 to 0.57.0 (#1680)
• f0061eb 🌱 Bump google.golang.org/grpc from 1.81.1 to 1.82.1 (#1687)
• 20ee732 🌱 Bump github.com/sigstore/cosign/v2 from 2.6.3 to 2.6.4 (#1685)
• 9f295ef 🌱 Bump the github-actions group with 6 updates (#1686)
• 69bf556 🌱 Bump github.com/sigstore/sigstore-go from 1.1.4 to 1.2.0 (#1681)
• 94e8b96 🌱 Bump github.com/sigstore/rekor from 1.5.0 to 1.5.2 (#1673)
• c7a1b37 🌱 Bump github.com/sigstore/fulcio from 1.8.5 to 1.8.6 (#1675)
• Additional commits viewable in compare view

Sourced from github/codeql-action/upload-sarif's releases.

v3.37.4

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

v3.37.3

No user facing changes.

v3.37.2

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

v3.37.1

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

v3.37.0

• Update default CodeQL bundle version to 2.26.0. #3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

v3.36.3

No user facing changes.

• a2983b8 Merge pull request #4058 from github/backport-v3.37.4-f205ea1c3
• 30d6d12 Rebuild
• 14e2e60 Update version and changelog for v3.37.4
• 5d3f01e Merge remote-tracking branch 'origin/releases/v4' into backport-v3.37.4-f205e...
• 3f405c7 Revert "Rebuild"
• 19d11a3 Revert "Update version and changelog for v3.37.3"
• f205ea1 Merge pull request #4053 from github/update-v4.37.4-9130ce0f7
• e40d079 Update changelog for v4.37.4
• 9130ce0 Merge pull request #4051 from github/update-bundle/codeql-bundle-v2.26.2
• c62d824 Add changelog note
• Additional commits viewable in compare view

Sourced from qltysh/qlty-action/coverage's releases.

v2.3.0

New

• Add a selected input to the coverage action for marking an upload as covering a selected subset of the test suite, which contributes to diff coverage only and is excluded from total coverage (#200)

v2.2.3

• Internal release process improvements (no user-facing changes) (#196)

v2.2.2

Fixed

• Security updates to bundled dependencies (#190, #191)

Sourced from qltysh/qlty-action/coverage's changelog.

Changelog

v2.3.0 (2026-07-09)

New

• Add a selected input to the coverage action for marking an upload as covering a selected subset of the test suite, which contributes to diff coverage only and is excluded from total coverage (#200)

v2.2.3 (2026-07-07)

• Internal release process improvements (no user-facing changes) (#196)

v2.2.2 (2026-07-07)

Fixed

• Security updates to bundled dependencies (#190, #191)

v2.2.1 (2026-06-02)

• Bump action runtime to node24

v2.2.0 (2025-08-11)

• Testing release process (no changes)

v2.1.0 (2025-08-08)

New

• support "dry-run" option for command complete

Improved

• Use log level "error" instead of "warning" when a catastrophic error occurs but "skip-errors" is true

Fixed

• Ignore "validate" option when command is "complete" (otherwise errors with invalid option)

v2.0.0 (2025-08-05)

This release mirrors the breaking change we introduced in the qlty CLI proper: we now validate coverage data by default instead of uploading coverage data to qlty that qlty cannot use. Now you must opt out of this behavior whereas previously opt in.

What This Means for You:

• If coverage reporting is working as expected, you'll experience no impact. If you're uploading valid reports and seeing directory and file-level coverage metrics in Qlty, you don't need to do anything. (If your reports include mismatched paths, you'll see specific path errors listed within your CI output)
• Potential CI Build Failures: Once this change is implemented, if your current CI/CD pipeline uploads a report with mismatched paths, your builds will begin to fail when executing qlty coverage publish.
• Quick Fix for Build Failures: If your builds start failing and you need to get them passing immediately, you can temporarily add validate: false to the GitHub Action configuration. This will disable validation and allow your CI build to pass (though your coverage data will remain broken until you've uploaded a valid report).

... (truncated)

• 08a0a86 Prepare release v2.3.0 (#201)
• 8b0d5e5 Add selected input to the coverage action (#200)
• dafbc1e Prepare release v2.2.3 (#197)
• bb4c677 Announce releases to #feed-deploys (#196)
• c9fe6ae Group security dependency fixes into one changelog item (#195)
• b413a89 Release v2.2.2 (#194)
• bbb11a9 Automate changelog drafting in the release process (#193)
• 3baf1fc Fix Dependabot alerts in .qlty/configs: js-yaml, ajv, @​eslint/plugin-kit (#192)
• 9341197 Fix @​opentelemetry/core Dependabot alerts: @​sentry/node 9 -> 10 (#191)
• 1d3373b Fix undici Dependabot alerts via root override to ^6.27.0 (#190)
• Additional commits viewable in compare view